Repository navigation
docs(readme): fix rename banner and repository links - #65
Merged
Merged
Conversation
Follow-up to the post-merge review of PR 64 (refs #63). - F1: point the banner link for #63 at openabdev/openab-computer. - F2: reword the banner. The executable, bundle id and paths keep their current names (oab-instance-mcp, dev.openab.instance-mcp) and will not change in this rename. The "until that rename ships" wording is removed. - F3: change the five remaining openabdev/instance-mcp URLs in README.md (two Releases links, the latest-release API call, the Linux download URL and the #45 issue link) to openabdev/openab-computer. Only repository URLs and prose changed. Executable names, asset filenames, config and log paths, LaunchAgent labels and the bundle id are unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #63
Discord Discussion URL: Not applicable - maintainer docs follow-up for #63